feat: upgrade account-crd chart #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Maybe @embik could also provide some insights with an estimation on what will happen 😉 |
aaronschweig
force-pushed
the
feat/account-crd-metadata-upgrade
branch
from
e410824 to
4f221d8
Compare
nexus49
force-pushed
the
feat/account-crd-metadata-upgrade
branch
from
adb92cf to
7873870
Compare
nexus49
approved these changes
Nov 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Caution
This updates the
APIResourceSchemawe don't know how KCP handles that - I hope not all the account resources get deleted when such an upgrade happens - we should monitor that.FYI @nexus49